home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Gigarom 1
/
Gigarom Macintosh Archives (Quantum Leap)(CDRM1080320)(1993).iso
/
FILES
/
APP
/
S-Z
/
UULite1.4.sea
/
UULite1.4.rsrc
/
TEXT_1026_Encoding Produces Empty Files.txt
< prev
next >
Wrap
Text File
|
1992-09-07
|
1KB
|
15 lines
"Encoding produces empty or very small files"
UULite should not be used to uuencode application programs. If you do, the result will be
useless, very small output files. This is because Macintosh-specific files have two sections
or forks, the resource fork and the data fork. Application programs on a Mac typically have
a large resource fork and a very small or nonexistent data fork. Image files, in formats
such as gif or jpeg, are contained entirely in the data fork. Because most other computers
have only data forks, these formats may be passed directly to and from them. The
uuencoding method used by UULite is the same standard method used by these
non-Macintosh computers, and will therefore encode only the data fork of files.
If you wish to encode a native Macintosh file that has a resource fork for transmitting over
a network to another Mac, use binhexing. You may think of binhexing as the Macintosh
equivalent of uuencoding. You should be aware that files that are binhexed
are only meant to be sent to other Macs.